Upgrade gitsheets ^1.4.1 → ^2.2.0. The 2.x line rewrites the
core in Rust (via @gitsheets/core-napi) but keeps the Node public
API surface (openRepo/openStore/Sheet/Transaction) unchanged.

Command run: npm install gitsheets@^2.2.0 -w apps/api

hologit is dropped as a transitive dependency in 2.x; it no longer
appears in the lockfile. Code migration (avatar blob-write path) is
in the next commit.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

gitsheets 2.x drops hologit as a dependency. Replace the
BlobObject.write(hologitRepo, buf) pattern with the 2.x surface:

  const blob = await repo.writeBlob(buffer: Buffer)  // → BlobHandle
  await sheet.setAttachments(record, { 'name.jpg': blob })

Sites migrated:
- apps/api/src/routes/people.ts: avatar upload (original + 128 thumb)
- apps/api/scripts/import-laddr/importer.ts: legacy avatar + blog-media

The `as unknown as string` casts are removed — 2.x writeBlob takes
a Buffer natively, matching the actual runtime types throughout.

The three workarounds for gitsheets#184 (swapPublic in store.ts,
git cat-file in attachments.ts, data-repo-lock.ts) are unaffected
and confirmed to still compile. They are kept as-is pending upstream
resolution.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

gitsheets 2.x (Rust core) refuses to marshal a null- or undefined-
valued field to TOML — `serializeRecords`/`upsert` throw "cannot
marshal JS value of type Null/Undefined to a TOML value". gitsheets
1.4.1 (`@iarna/toml`) silently dropped such keys, so they were never
written to disk (verified against the on-disk `published` snapshot —
no record carries a null-valued key).

Our Zod schemas mark optional fields `.nullable().optional()` and the
write services normalize cleared fields to `?? null`, so under 2.x
every write of a record with a cleared optional field threw a 500.
This surfaced as 16 test failures across write-api, people-lifecycle,
and import-laddr (all "cannot marshal ... Undefined/Null").

Fix: wrap the per-sheet Standard Schema validator in openPublicStore
so the validated record has null/undefined-valued keys stripped
(recursively) before it reaches the core marshaller. gitsheets runs
the validator host-side and marshals its output, so this is the
single authoritative write boundary. The result is byte-identical to
1.4.1's on-disk form: an absent optional field is an absent TOML key.

This is not one of the two documented 2.x re-baselines (integer
underscores, markdown bodies) — it's an undocumented marshal-contract
change in the Rust core that the upgrade plan did not anticipate.

Adds a focused store test asserting null-valued keys are dropped and
present fields survive (also pins the integer-underscore re-baseline).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…tion

Record the undocumented null/undefined marshal-contract change found
during the bump (Rust core throws where 1.4.1 dropped the key) and the
stripNullish fix at the write boundary. Check off the validation
checklist; note no test needed a re-baseline update.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The `not.toContain('null')` check tripped on the fixture's own
"Nullish Person" / "nullish-person" strings. The three field-absence
regexes above already verify null-valued keys aren't written; replace
the broad substring check with `not.toMatch(/=\s*null\b/)` — no field is
assigned a bare null value.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>